The bot logic was centralized in th30d4y/.github but not consumable in a standardized way across all org repositories. This change introduces a reusable workflow contract plus a thin caller template so each repo can trigger the same bot behavior on new issues/PRs with org-level secrets and permissions.

• Reusable workflow contract (.github/workflows/org-bot.yml)

  • Added workflow_call support with explicit inputs (event_type, number, title, url) while preserving native issues.opened / pull_request.opened triggers.
  • Unified metadata extraction and comment/email flow so the job works both when triggered directly and when invoked from another repo.
  • Hardened input/number handling for called-workflow execution paths.

• Standard per-repo caller template (.github/workflow-templates/)

  • Added org-bot-caller.yml template that listens to issues.opened and pull_request.opened and forwards normalized event data to the centralized workflow.
  • Added template metadata via org-bot-caller.properties.json for discoverability and reuse in rollout campaigns.

• Org rollout guidance (README.md)

  • Documented org secret requirements (EMAIL_USER, EMAIL_PASS) and repository permission expectations (issues: write, pull-requests: write).
  • Documented rollout strategy (pilot repos first, then broad rollout) and enforcement options (required workflows/rulesets when available).

jobs:
  org-bot:
    uses: th30d4y/.github/.github/workflows/org-bot.yml@main
    with:
      event_type: ${{ github.event_name == 'issues' && 'Issue' || 'Pull Request' }}
      number: ${{ github.event.issue.number || github.event.pull_request.number }}
      title: ${{ github.event.issue.title || github.event.pull_request.title }}
      url: ${{ github.event.issue.html_url || github.event.pull_request.html_url }}
    secrets: inherit